home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
QRZ! Ham Radio 3
/
QRZ Ham Radio Callsign Database - Volume 3.iso
/
digests
/
tcp
/
930222.txt
< prev
next >
Wrap
Internet Message Format
|
1994-06-04
|
7KB
Date: Mon, 30 Aug 93 04:30:05 PDT
From: Advanced Amateur Radio Networking Group <tcp-group@ucsd.edu>
Errors-To: TCP-Group-Errors@UCSD.Edu
Reply-To: TCP-Group@UCSD.Edu
Precedence: Bulk
Subject: TCP-Group Digest V93 #222
To: tcp-group-digest
TCP-Group Digest Mon, 30 Aug 93 Volume 93 : Issue 222
Today's Topics:
bmh v0.3
KA9Q Speaks!
PI CARD PROBLEMS
X1J TNC Code
Send Replies or notes for publication to: <TCP-Group@UCSD.Edu>.
Subscription requests to <TCP-Group-REQUEST@UCSD.Edu>.
Problems you can't solve otherwise to brian@ucsd.edu.
Archives of past issues of the TCP-Group Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives".
We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party. Your mileage may vary. So there.
----------------------------------------------------------------------
Date: Mon, 30 Aug 1993 01:24:26 +0100
From: Paul Healy EI9GL <Paul.Healy@cs.tcd.ie>
Subject: bmh v0.3
To: tcp-group@ucsd.edu
I have put a new version of bmh into incoming at ucsd.edu. The files
concerned are:
bmh03.txt : this message
bmh03exe.zip : documentation, bmh.exe, example.rc, copyrigh.bm
bmh03src.zip : documentation, source files for Turboc V2.0,
turboc.cfg, example.rc, copyrigh.bm
bmh03ps.zip : postscript version of the manual (to be uploaded a
little later today).
The bmh package is an unbundled bm for NOS running under MSDOS. It
allows the listing, reading and sending of mail from the MSDOS
command line. The user interface is based on the mh mail handler
found on many unix machines. The bmh program itself is a wrapper
program similar in functionality and feel to bm.
There is a small amount of support for news (nntp) reading and
posting.
New to this version are better documentation, mail, pick, refile and
lots of bug fixes. There is also an ax25 pbbs export program.
Paul
------------------------------
Date: Sun, 29 Aug 93 17:44:49 PDT
From: orvb@micom.com (Orville Beach (MIS))
Subject: KA9Q Speaks!
To: tcp-group@ucsd.edu
Phil Karn, KA9Q, has graciously consented to speak at HamVenture '93
(aka the ARRL Southwestern Division Convention). He's going to
discuss some of the shortcomings of current amateur digital protocols,
and his thoughts on how we might be able to get around those
deficiencies.
The ARRL Southwestern Division Convention will be held in Ventura,
California, on Sept. 17th-19th, at the Holiday Inn. (KA9Q's talk
will be held on Saturday the 18th).
Any questions, please feel free to contact Orv Beach, WB6WEY @ W8AKF
--
*****************************************************
| Orville Beach @ Micom Communications Corp. |
| Internet: orvb@micom.com Voice: (805)583-8600 |
*****************************************************
------------------------------
Date: Sun, 29 Aug 93 10:37:00 -0600
From: karl.ebel@drig.com (Karl Ebel)
Subject: PI CARD PROBLEMS
To: TCP-GROUP@UCSD.EDU
hello all,
we in a group of 4 stations run a small 56kB net, all with nearly the
same
hardware and software:
. MMT 432/28 transverter
. DSY modem 56kB, WA4DSY
. Ottawa PI card, serial # 86 ...
. NE2000 ethernet card clone
. 80386-25MHz PC motherboard !!
. PI packet driver, release 3 from ve3ifb
. Clarkson packet driver NE2000.COM ethernet
. JNOS version 108d
. DOS 5.0 / OS2 V2.0 in a DOS session
This configuration works perfectly, for years. But nothing stays the
same
over years.
A member of the group had to replace the motherboard, a new 486dx-33. No
problem, he thought. But this endend up in a useless system. No connects
on the 56KB channel anymore. Some tests showed the PI card sends
randomly
inserted FF-bytes in the packet stream. More tests showed CPU
clockspeeds
above 25MHz do not work, the PI card sends junk. This is independed from
the BUS clock speed. Some 33MHz boards work but you have to run through
this procedure, sometimes several times:
poweron-boot-test-notok-poweroff-poweron-boot-test-ok...
All other modes work as usual, ethernet runs, async runs, no problems.
Can anyone help us? Where can i find Dave Perry, VE3IFB. He wrote the
PI card driver software, and perhaps he knows about timing problems the
PI card may have.
But the story is not at an end. We had the idea to upgrade OS2 from V2.0
to V2.1. You need no strong imagination to predict what happened. The
PI card does not work anymore. The JNOS system crashes at a moment where
the PI card starts to send. Receiving with the PI card works. The rest
of
the system works, ethernet NE2000, all async interfaces..
Inspection of what the PI card sends show a bad sendbuffer pointer. JNOS
is able to support the PI card in two different ways, by an internal,
compiled-in, driverfunction or by the TSR driver from ve3ifb. Both
versions show the same failure. There seems to be something bad in the
handling of DMA in a DOS session of V2.1 OS2.
Does anyone experiment with JNOS - OS2 V2.1 - PI card and can give us
some hints what to do? We are nailed to the past with our 56KB network.
No progress??
Thanks for any comments,
Karl.
+------------------------------------------------------------------------
---+
| Internet ..: karl.ebel@drig.com
|
| AMPRNET ...: charly@dk8gd.ampr.org 44.130.32.1
|
| BBS Mail ..: dk8gd@db0iz Germany Cologne
|
+------------------------------------------------------------------------
---+
------------------------------
Date: 29 Aug 93 13:44:11
From: ssampson@n5owk.ampr.org (Steve R. Sampson)
Subject: X1J TNC Code
To: TCP-Group@UCSD.Edu
Just a note to report on the X1J node software. I didn't try X1H
because of the bug reports, but figured I'd give er a go with this
version. I made the TNC mod as directed (put another socket
between the ROM and original socket, with pin 1 bent over) and that
took all of a couple minutes. I had to reburn the ROM though because
the first file was two bytes short and I did a simple binary copy to
combine them (nope, nope) but when I fixed this all was working well.
The only hurdle left was learning to specify the whole IP address as:
44.0.0.0 /8 instead of 44 /8
No biggy there. Result: this is really a nice router, able to replace
PC's at remote sites. You can even disable all the netrom stuff and
merely connect to it to update the ARP and IPRoute entries. I'd like
to see a version that has no netrom and fits in a 256k ROM. I don't
think the Deviation meter will be that valuable though, because weak
stations and other variables will give you wild results. Maybe a new
mod that only passes signals over S-9 to filter out the bad readings.
Looks good.
73, Steve N5OWK
------------------------------
End of TCP-Group Digest V93 #222
******************************
******************************